A federated call failed  to establish due to a media connectivity failure where one endpoint is internal  and the other is remote

hi There, in my environment, none of the users are able to share their desktop with remote domain users. call fails as soon as they make any sharing. looking at the Lync diagonostic report I see the below error. Any idea what must be wrong in my environment, as i'm clueless to move further on this issue?

Note: This issue does not occure when they are in the local LAN, but it hapens when they use internet or wifi network. Is it something i need to validate from network aspect? 

Below the Diagnostic header from monitoring server:

26; reason="A federated call failed to establish due to a media connectivity failure where one endpoint is internal and the other is remote"; CallerMediaDebug="application-sharing:ICEWarn=0x4000320,LocalSite=95.96.46.216:60279,LocalMR=84.207.228.206:52857,RemoteSite=10.48.0.127:50016,RemoteMR=87.213.105.251:52936,PortRange=60200:60299,LocalMRTCPPort=52857,RemoteMRTCPPort=52936,LocalLocation=1,RemoteLocation=2,FederationType=1"




October 7th, 2014 3:46pm

The problem is network connectivity 

Please refer to 

http://dusk1911.wordpress.com/2011/11/28/lync-audiovideo-not-working/

and also 

http://www.ucprimer.com/tech-blog/ms-client-diagnostics-23-reasoncall-failed-to-establish-due-to-a-media-connectivity-failure-when-one-endpoint-is-internal-and-the-other-is-remotecalleemediadebugaudioicewarn0x80012b

assuming Lync to Lync Im works fine 

Free Windows Admin Tool Kit Click here and download it now
October 7th, 2014 4:32pm

Hi,

It should be network issue.

You need to double check ports for Edge External.

For Edge External interface:

Make sure the following ports open: SIP/MTLS/5061 (in/out), SIP/MTLS/5061 (in/out), RTP/TCP/50K range (out)

More details:

http://technet.microsoft.com/en-us/library/gg425891(v=ocs.14).aspx

Best Regards,

Eason Huang

October 8th, 2014 8:39am

Please, Check firewall ports.

http://technet.microsoft.com/en-us/library/gg425891(OCS.14).aspx

443: Client to server SIP traffic for remote user access

5061: Federation and connectivity with a hosted Exchange service

50,000-59,999: Media exchange, Application sharing/desktop sharing and File transfer

Free Windows Admin Tool Kit Click here and download it now
October 8th, 2014 8:51am

yes Lync to Lync IM works fine.

my problem is quite confusing really...

Application sharing does not work with one specific federated domain only over internet , but the same works on the LAN. my trouble here is, the same application sharing  does work well with any other federated domain over the same internet connection. because of the above reason i'm unable to confirm its a network or port related issue. any idea how can i segregate the issue now?

October 8th, 2014 2:21pm

my problem is quite confusing really...

Application sharing does not work with one specific federated domain only over internet , but the same works on the LAN. my trouble here is, the same application sharing  does work well with any other federated domain over the same internet connection. because of the above reason i'm unable to confirm its a network or port related issue. any idea how can i segregate the issue now?

Free Windows Admin Tool Kit Click here and download it now
October 8th, 2014 2:21pm

Are you remote clients able to have audio video call with your internal user 

I would suggest from an external network test your setup and your federated setup if you have test account 

using https://testconnectivity.microsoft.com/ audio test options

October 8th, 2014 3:35pm

I'm seeing this exact situation. What did you find as the cause and how is it fixed?
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 4:10pm

using https://testconnectivity.microsoft.com/ audio test options
August 13th, 2015 2:20am

this issue was fixed after we fine tune our firewall settings, here is what we did.

Basically Lync is using an anonymous Cipher (TLS_DH_anon_WITH_RC4_128_MD5) for TCP traffic, this was previously not allowed in our firewall so the connections were dropped by firewall, hence we had to enable this in fireall in order to resolve this issue. you may either enable TCP or UDP for this chipher, but UDP is the most preferable option.

Free Windows Admin Tool Kit Click here and download it now
August 19th, 2015 1:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics